home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Netware Super Library
/
Netware Super Library.iso
/
nov_info
/
fyi14
/
02111.dos
< prev
next >
Wrap
Text File
|
1991-02-11
|
2KB
|
42 lines
Number: A3TH091490U668
Subject: Spurious and Lost Interrupts
Date: September 14, 1990
- - - - - - - - - - - - - - - - - - - - - -
GENERAL
INFORMATION: In order to explain what a lost or spurious interrupt is, we
will explain how an interrupt is generated and then what
generates the lost or spurious interrupt.
When an I/O peripheral (such as a LAN card or disk
controller) requests attention it will generate an interrupt
to the Programmable Interrupt Controller (PIC) by asserting
the IRQ line with a voltage and will hold that voltage
constant. The PIC will then assert an INT signal to the
CPU. After the CPU is available to service the interrupt,
it will respond with an INTA signal. The PIC will poll the
IRQ lines and determine which interrupt was generated and
the PIC will respond with the appropriate interrupt
information on the data bus. The CPU will then execute the
appropriate code (Interrupt Service Routine or ISR)
associated with the interrupt vector returned by the PIC.
With this in mind, lets discuss what causes a lost
interrupt. After the CPU responds with an INTA signal, the
PIC will poll the IRQ lines to determine which peripheral
caused the interrupt. If the I/O peripheral drops the line,
the PIC will have no way of knowing who caused the interrupt
and will generate a hardware interrupt 7. The NetWare OS
ISR for interrupt 7 is executed which displays the lost
interrupt error message.
Spurious interrupts are generally associated with shared
interrupts. When a shared interrupt is generated, the PIC
must query each I/O peripheral to determine who needs
attention. If no device claims responsibility, the spurious
interrupt error message will be displayed and the interrupt
ignored.
(X) This information was verified by Engineering.